-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Neurips23] NGT Submission for OOD track #187
Conversation
@masajiro thanks for the PR. I am not able to run this to completion. I am attaching the trailing log from my VM. Could you please help me debug..
|
Thanks for checking. We have confirmed that this program runs on Standard D8lds v5. It might be because other processes are using memory and there is not enough memory for this program to run. |
When you run it again, the half-finished index data/indices/ood/ngt must be removed. |
OK, I was trying to debug repeated crash and realized this was happening :) Anyway, thanks for the warning. Is it possible to set up your submission to clean up from crashes -- it would make the overall benchmark framework easier to rerun/replicate in the future. Thanks! |
I would like to know the exact available memory of your azure server. The available memory of our azure server (Standard D8lds v5) is about 15.4 G from the following commands. $ free
total used free shared buff/cache available
Mem: 16362296 557696 177124 4452 15627476 15445464
Swap: 0 0 0 $ grep Mem /proc/meminfo
MemTotal: 16362296 kB
MemFree: 176876 kB
MemAvailable: 15445216 kB |
I am the only user logged in and yours is the only job I ran. I did so last time as well. I see a similar problem again.
After the crash, I see
Could you please consider tuning down your index build to use 0.5GB less DRAM to allow for fluctuations in available memory? |
Thank you for your information. It is strange that there is no small difference in the available memory. Anyway, we will try to reduce the memory usage to less than 15.0 GB. |
The peak VM size of this latest commit is 14.98G. Could you please check this out? |
I see the following crash now (I did remove previous index files before launching the run):
|
I assume that the available memory is gradually decreasing. We don't see this situation on our servers. If you could delete the directory |
When you rerun it as mentioned above, please confirm that 15.0 G is available. The following command may help you find processes that are wasting memory.
|
@harsha-simhadri |
The parameters are finalized. |
@harsha-simhadri |
@harsha-simhadri It worked for me, but I was testing on c6i.2xlarge.
The peak VM size seemed to have been
|
Merging this, thanks for your submission @masajiro. |
@maumueller |
This is an improved version of NGT ONNG. Please check it out.